Rebased and fixed to be up to date with main

@querdenker2k do you see why some of the ITs are failing?

It's because all rules are disabled by default and they are not triggered.
Adding rule: org.openhab.automation.jrule.rules.user.TestPersistence@421cba65, enabled: false

Nice. I'll try to review shortly.

Some comments so far, just tested it. I really like this a lot!

• Would it be better to write out what rules are disabled ? Now it is a warning saying "Note X rules are disabled")
• Should we add an annotation to disable a rule?
• Enable / Disable seems to work
• Run now on rule does not seem to work (also mentioned in documentation so it's ok but would be a cool feature)
• JRuleLoadingStatistics could possibly be reset, cleared instead of creating a new instance to follow similar pattern as ruleprovider etc
• Tests are failing for me, not sure if it is an intermittent problem that is not caused by this PR.

1. Writing out disabled rules; agreed
2. Yes. Also been thinking about the ability to programmatically enable/disable rules, but have not made up my mind if this is an anti-pattern that instead should be resolved with preconditions
3. Correct, it would require generating config for input data. Initially I tried to provide more info about the triggers, but did not figure out how to do this unless using existing predefined concepts that would not always match JRule
4. Yes
5. They are running on my side atm, but I think we have a timing/concurrency issue in general that should be resolved. When I reboot openHAB rules are compiled and loaded from 1-3 times. We might need to introduce the ReadyService mechanism or change the osgi start level - or something totally different. Have not investigated.